Preprocessing correction #113
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #113 +/- ##
========================================
- Coverage 4.40% 2.79% -1.61%
========================================
Files 36 46 +10
Lines 2815 4430 +1615
Branches 0 727 +727
========================================
Hits 124 124
- Misses 2691 4306 +1615 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
|
there are many changes in the version number. Please keep them updated with the 0.6.1, and do not change them. @JairMathAI |
JairMathAI
deleted the
correction/preprocessing_implementation_uncertainty_maps
branch
Contributor
Author
|
@jxchen01 you are right I already did the correction thank you so muchm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my last implementation I forget to take into account the preprocessing step now it's corrected.